[Chore] Run webview CI tests with four workers (#2288) - #2308

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

Related GitHub Issue

Closes: #2288

Description

The webview CI Vitest run now uses four workers on hosted runners. The previous budget was one worker. The change is one line in webview-ui/vitest.config.ts: maxWorkers: isCI ? 4 : undefined (was isCI ? 1 : undefined). The setting applies only when CI=true, so it covers the measured Ubuntu and Windows hosted runner classes. Local (non-CI) runs stay unchanged.

Forks, isolation, assertions, coverage, onConsoleLog handling, and CI test timeouts are unchanged. The default forks pool stays in place. No benchmark harness is included in this PR. Vitest stays at 4.1.12. No errors are suppressed.

Benchmark

From #2288 (GitHub-hosted benchmark, commit 86197abe, Node 22.23.4 / Vitest 4.1.12, two repetitions per setting, 174 files / 2,269 tests, no retries):

Local Linux spot-check for this PR (18 vCPU, CI=true): the src/components subset (147 files / 1,799 tests) took 235.8s with --max-workers=1 and 108.9s with the new four-worker config.

Once CI runs on this PR, compare test-step duration, job duration, runner minutes, and time until required checks turn green against main. Two repetitions do not establish reliability or p95.

Rollback

Revert the worker budget to one worker. Change maxWorkers: isCI ? 4 : undefined back to maxWorkers: isCI ? 1 : undefined in webview-ui/vitest.config.ts, or revert this commit. No other cleanup is required.

Test Procedure

• CI=true pnpm turbo run test:coverage --filter=@roo-code/vscode-webview: 181 files / 2,333 tests passed, 133.1s (full inventory with coverage, four workers, Linux).
• Same src/components subset with --max-workers=1 vs the new config: 235.8s vs 108.9s.
• pnpm --filter @roo-code/vscode-webview lint: pass.
• pnpm --filter @roo-code/vscode-webview check-types: pass.
• pnpm exec prettier --check webview-ui/vitest.config.ts: pass.
• Root pnpm test: pass on rerun (14/14 Turbo tasks). One earlier run had two failures in src/__tests__/extension.spec.ts under heavy parallel load. That file passes 24/24 in isolation. The failures are unrelated to this change.
• Reviewers: watch the platform-unit-test jobs of the Code QA workflow on this PR.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I reviewed my own code with care.
• Writing Style: The PR title and description use Simplified Technical English (ASD-STE100): short sentences, plain words, active voice, one idea per sentence, no contractions.
• Testing: New and/or updated tests have been added to cover my changes (if applicable). (N/A: config-only change. The existing inventory proves the contract.)
• Test Helpers (test changes only): (N/A: no test changes.)
• Visual Snapshot (UI changes only): (N/A: no UI change.)
• Documentation Impact: I checked if my changes need documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I read and agree to the Contributor Guidelines.

Visual Snapshots

Not applicable. This change does not alter rendered UI.

Videos (interaction / animation only)

Not applicable.

Documentation Updates

• No documentation updates are required.
• Yes, documentation updates are required.

Additional Notes

Issue #2288 notes a rare Ubuntu teardown error, Closing rpc while "onUserConsoleLog" was pending, seen once in twelve benchmark repetitions. The upstream fix ships in Vitest 5.1.0-beta.1. This repo uses Vitest 4.1.12. That issue is tracked separately and is not addressed here.

Get in Touch

0x7777777_